After changing sim resolution, it won`t simulate

[hardrock_ram]

I have just switched to PhoenixFD 3.00.01 from official 2.2.

I am doing a simple smoke simulation. It all works fine at the given sim resolution, the smoke is thick and works just fine.
But when I change the sim resolution either up or down, it won`t simulate. Or rather, it seems to be working since it takes some time on each frame, but nothin shows up in the render window, and the .aur-files are empty.

It also doesn`t help to change the resolution, save and reopen the file. It still won`t work as it should. But if I change the resolution back to the original, it will simulate fine again.

This was never an issue in 2.2, so it seems like a bug to me. Do you have a solution?

[Svetlin.Nikolov]

Can you give us more info on that? Do you change the cell size or the grid size? Are your input and output paths at defaults?

[hardrock_ram]

I changed the cell size. Specifically I used the increase\decrease resolution buttons.
My output path is set to a different location, and it does save an actual .aur-file. Its just that every file is 1kb big, no matter how many frames it has simulated.
I made sure that the only change I did was to resolution. Everything else stays the same.
I also did a test where I increased the output velocity in the source by x10, increased the quality of the conservation etc, but nothing changes. The only thing that can make it simulate properly again is to change the resolution back to the original value.
Lastly, I have also tried to manually remove all .aur- and settings files, but it didn`t help.

[Svetlin.Nikolov]

If the new caches are 1kb big, there is something wrong. Can you try 3.00.02 from the website?

[hardrock_ram]

Sure I`ll get back to you after I have tried.

[hardrock_ram]

3.00.02 behaves the exact same way unfortunately

[Svetlin.Nikolov]

Any chance you could send us the scene with the exact steps to reproduce it? This would be very helpful and we should have that fixed quickly.

[hardrock_ram]

No problem .
The file is approx. 300mb large. How should I proceed?

[Svetlin.Nikolov]

Ah, then you should drop a mail to Support and they will give you the instructions for uploading to their FTP

Thanks very much!

[hardrock_ram]

I have sent a mail to support

[hardrock_ram]

Can this issue be related to the problem I described in the thread "PhoenixFD 3.0 doesn`t handle user defined properties correct"?

For me it seems unlikey ... But since I am apparently the first reporting this bug, along with the fact that I use user defined properties all the time, there is a slight chance there is a connection there

[hardrock_ram]

The file is now uploaded. Its name is: chaosgroup_pxfdProblems.rar

Please take this problem into account: http://forums.chaosgroup.com/showthr...erties-correct
It is in the same file.

Support is also notified

[Svetlin.Nikolov]

Hello,

Got it, but the issue is with the scene geometry - all the geometry that interacts with Phoenix needs to be 'watertight' - there must be no open geometries and planes, and all the normals must always point either outside the geometry volume, or inside. If the geometry does not fit these conditions, it's a matter of luck whether you'll get a freezing simulation, no source output or explosions, which would depend on the grid resolution and where the objects is placed. We have many signals that we need to add a system that would warn you if the geometries you use inside the simulator are not correct, but for now you can try this: switch the Interaction mode from Exclude to Include and first add all the sources and the emitter geometries, and then start adding the important obstacles for the simulation, making sure they are watertight.

This should solve the problem

[hardrock_ram]

Ok, good to know. Thanks for looking into it

[hardrock_ram]

Ok, the simulation issue is fixed now. Thanks

Another problem is that I can`t get the include\exclude list to work. It is is set on anything else than "exclude list" with an emplty list, it won`t simulate. I had the exact same problem on 2.2 as well. I am working on the same file as you recieved. What can the cause for that be?